Choose how data refreshes
Distinguish a saved record, a refreshed screen, polling, and live subscriptions.
A database write and an updated screen are different outcomes. Decide how the interface should obtain the latest records after each important action.
Start with a visible refresh
Configure the read action that supplies the screen, then test what happens after a record is created or edited. If the displayed list does not update, review the flow and response mapping rather than assuming that saving automatically reloads every component.
Use the behavior your flow configures
The HTTP Request action can enable long polling for repeated GET requests, with an interval and a maximum-request count. This repeatedly asks for data; it is different from a server pushing an update.
The Supabase action runtime includes subscription support for configured flows. Review the selected table, query, access rules, and mapping before depending on live behavior.
Verify with a second view
Make a sample change, inspect the saved record, and check another browser view. Test losing and restoring a connection, an empty result, and a record that the current user cannot read.
Values saved only through Save To Local Storage belong to that browser's local storage. They are not shared, account-wide database synchronization.